摘要 :
Today''s large software projects are often characterised by distributed environments with numerous developers separated in space and/or time. This separation means that the common understanding and tacit knowledge that is a featur...
展开
Today''s large software projects are often characterised by distributed environments with numerous developers separated in space and/or time. This separation means that the common understanding and tacit knowledge that is a feature of closely colocated project teams is very hard to come by. As a consequence, relatively simple tasks such as identifying functionally related modules or finding individuals who are experts in aspects of the system become more challenging and time-consuming. This paper presents a Continuum of Relevance Index (CRI) model that uses information gathered from developer IDE interactions to generate orderings of relevant tasks, project artefacts and developers. A case study is used to demonstrate how the model can be used to attain a shared knowledge and common understanding of the extent to which tasks, artefacts and developers are relevant in a group development work context.
收起
摘要 :
Today''s large software projects are often characterised by distributed environments with numerous developers separated in space and/or time. This separation means that the common understanding and tacit knowledge that is a featur...
展开
Today''s large software projects are often characterised by distributed environments with numerous developers separated in space and/or time. This separation means that the common understanding and tacit knowledge that is a feature of closely colocated project teams is very hard to come by. As a consequence, relatively simple tasks such as identifying functionally related modules or finding individuals who are experts in aspects of the system become more challenging and time-consuming. This paper presents a Continuum of Relevance Index (CRI) model that uses information gathered from developer IDE interactions to generate orderings of relevant tasks, project artefacts and developers. A case study is used to demonstrate how the model can be used to attain a shared knowledge and common understanding of the extent to which tasks, artefacts and developers are relevant in a group development work context.
收起
摘要 :
Distributed Software Development involves a number of different business models, and companies intending to embark on the journey of distributed development have difficulty choosing the model(s) that suits their process and curren...
展开
Distributed Software Development involves a number of different business models, and companies intending to embark on the journey of distributed development have difficulty choosing the model(s) that suits their process and current software practice. More literature that presents similarities as well as differences among these models, in terms of processes, practices and challenges that characterize them, is thus becoming critical to software practitioners. This paper intends to bring more knowledge in this direction. We present empirical evidence from a case study of DSD practice in five companies that had projects following one or more of the different DSD business models described in the literature. We discuss the similarities and differences in the challenges faced by the projects in these models, as well as the relationship between the models, development process, and project size and complexity, as reported in the projects studied.
收起
摘要 :
Distributed Software Development involves a number of different business models, and companies intending to embark on the journey of distributed development have difficulty choosing the model(s) that suits their process and curren...
展开
Distributed Software Development involves a number of different business models, and companies intending to embark on the journey of distributed development have difficulty choosing the model(s) that suits their process and current software practice. More literature that presents similarities as well as differences among these models, in terms of processes, practices and challenges that characterize them, is thus becoming critical to software practitioners. This paper intends to bring more knowledge in this direction. We present empirical evidence from a case study of DSD practice in five companies that had projects following one or more of the different DSD business models described in the literature. We discuss the similarities and differences in the challenges faced by the projects in these models, as well as the relationship between the models, development process, and project size and complexity, as reported in the projects studied.
收起
摘要 :
Community smells are symptoms of organizational and social issues within the software development community that often increase the project costs and impact software quality. Recent studies have identified a variety of community s...
展开
Community smells are symptoms of organizational and social issues within the software development community that often increase the project costs and impact software quality. Recent studies have identified a variety of community smells and defined them as sub-optimal patterns connected to organizational-social structures in the software development community such as the lack of communication, coordination and collaboration. Recognizing the advantages of the early detection of potential community smells in a software project, we introduce a novel approach that learns from various community organizational and social practices to provide an auto-mated support for detecting community smells. In particular, our approach learns from a set of interleaving organizational-social symptoms that characterize the existence of community smell in-stances in a software project. We build a multi-label learning model to detect 8 common types of community smells. We use the ensemble classifier chain (ECC) model that transforms multi-label problems into several single-label problems which are solved using genetic programming (GP) to find the optimal detection rules for each smell type. To evaluate the performance of our approach, we conducted an empirical study on a benchmark of 103 open source projects and 407 community smell instances. The statistical tests of our results show that our approach can detect the eight considered smell types with an average F-measure of 89% achieving a better performance compared to different state-of-the-art techniques. Furthermore, we found that the most influential factors that best characterize community smells include the social network density and closeness centrality as well as the standard deviation of the number of developers per time zone and per community.CCS CONCEPTS• Software and its engineering → Software organization and properties.
收起
摘要 :
Any global software development project needs to deal with distances -- geographical, cultural, time zone, etc. -- between the groups of developers engaged in the project. To successfully manage the risks caused by such distances,...
展开
Any global software development project needs to deal with distances -- geographical, cultural, time zone, etc. -- between the groups of developers engaged in the project. To successfully manage the risks caused by such distances, there is a need to explicate and present the distances in a form suitable for manual or semi-automatic analysis, the goal of which is to detect potential risks and find ways of mitigating them. The paper presents a technique of modeling a global software development project suitable for such analysis. The project is modeled as a complex socio-technical system that consists of functional components connected with each other through output-input relationships. The components do not coincide with the organizational units of the project and can be distributed through the geographical and organizational landscape of the project. The modeling technique helps to explicate and represent various kinds of distances between the functional components to determine which of them constitute risk factors. The technique was developed during two case studies, of which the second is used for presenting and demonstrating the new modeling technique in the paper.
收起
摘要 :
As part of a research project dedicated to the Social Organizational and Cultural Aspects of Global Software Development, the author has chosen to focus on collaborative work practices and knowledge management aspects of collabora...
展开
As part of a research project dedicated to the Social Organizational and Cultural Aspects of Global Software Development, the author has chosen to focus on collaborative work practices and knowledge management aspects of collaborative work. More precisely, the focus is on how the global distribution of software development affects collaborative work. The current paper is a first attempt to unveil, through a concrete situation observed in a distributed software development environment, the complex ways in which people use technology to establish collaborative work practices. By using ethnographically-informed methods, the author presents a bottom-up study of actual work practices, meant to contribute to a better understanding of collaborative work and knowledge management processes in distributed software development.
收起
摘要 :
As part of a research project dedicated to the Social Organizational and Cultural Aspects of Global Software Development, the author has chosen to focus on collaborative work practices and knowledge management aspects of collabora...
展开
As part of a research project dedicated to the Social Organizational and Cultural Aspects of Global Software Development, the author has chosen to focus on collaborative work practices and knowledge management aspects of collaborative work. More precisely, the focus is on how the global distribution of software development affects collaborative work. The current paper is a first attempt to unveil, through a concrete situation observed in a distributed software development environment, the complex ways in which people use technology to establish collaborative work practices. By using ethnographically-informed methods, the author presents a bottom-up study of actual work practices, meant to contribute to a better understanding of collaborative work and knowledge management processes in distributed software development.
收起
摘要 :
Benefits of distributed software development are discussed controversially. What is perceived as benefit in one case, may be only partially realizable, a disadvantage or even a myth in another one. This paper is a report on the re...
展开
Benefits of distributed software development are discussed controversially. What is perceived as benefit in one case, may be only partially realizable, a disadvantage or even a myth in another one. This paper is a report on the results of an empirical study about distributed requirements engineering practice. The identified benefits are discussed according to related interpedendencies which show the Janus-faced nature of benefits and challenges in distributed project settings.
收起
摘要 :
Benefits of distributed software development are discussed controversially. What is perceived as benefit in one case, may be only partially realizable, a disadvantage or even a myth in another one. This paper is a report on the re...
展开
Benefits of distributed software development are discussed controversially. What is perceived as benefit in one case, may be only partially realizable, a disadvantage or even a myth in another one. This paper is a report on the results of an empirical study about distributed requirements engineering practice. The identified benefits are discussed according to related interpedendencies which show the Janus-faced nature of benefits and challenges in distributed project settings.
收起
原文获取